19004 A new statement was started while another statement was in progress.
19005 Multiple columns were returned for a FetchString command. These must only return one column.
19006 Multiple rows were returned for a FetchString command. These must be written to only return one row.
19007 Unsupported numeric precision: %precision%.
19008 API protocol violation: the database connection has not been opened.
19009 API protocol violation: the statement has not yet been initialized.
19010 Invalid parameter number.
19011 Invalid buffer address.
19012 For character types, the coldef parameter must contain the precision of the field as defined in the schema.
19013 API protocol violation: the statement has not been prepared.
19014 API protocol violation: this option must be set before the statement is prepared.
19015 Invalid column number.
19016 Invalid buffer max length.
19017 Invalid buffer for length returned.
19018 This type of fetch request is invalid for the current cursor type.
19019 Invalid row index %ix%, rowset size is %rowset size%.
19020 Invalid column number: %colno%.
19021 Invalid timestamp: "%timestamp%". Must be in format yyyy-mm-dd hh:mm:ss.
19022 Bad return %rc% from SQLError() when trying to get the message for a bad return from %context%.
19023 Invalid token for deferred parameter (token at %token%).
19024 Unsupported dbms vendor name: %name%.
19025 Invalid type %type% for deferred parameter %param%. Must be PD_SQL_LONGVARCHAR.
19026 Invalid request to position cursor to rowset position %position%. The position must be between 0 and the rowset size %max%.
19027 got PdDb resources
19028 Unsupported dbms vendor name: %name%.
19029 The version of the current database is %is%. This script can only be applied to a database of version %need%.
19030 The table %table% currently contains %count% rows. This script can only be applied to a database in which this table is empty.
19031 There are currently %count% rows in table %table% that have %value% as the value of column %field%. This script cannot be applied unless no rows use this value for this column.
19032 The following fields do not make a unique index on table %table%: %fields%. This script cannot be applied unless there are no duplicate values for these fields.
19033 The schema name of the current database is %is%. This script can only be applied to a database whose schema name is %need%.
19034 The field %table%.%field% has a value of %result%. This script can only be applied to a database whose %table%.%field% has a value of %value%.
19035 A PdDbGuard object currently has control over commits and rollbacks for this PdDatabase object. You must use the features of the PdDbGuard to commit or rollback; you must not use this object's own ::Commit or ::Rollback members while the PdDbGuard object is active.
19036 File too large for inserting into database. Maximum size is %maxsize% bytes; this file, %filename% is %filesize% bytes.
19037 The version of MS Sql Server ODBC driver is incompatible. It is at version %curr_version% but it must be %version% or higher.
19038 No data was returned for query %sql%.
19039 The table %table% already contains a column named %column%. This upgrade cannot be applied to this database until this situation is resolved.
19040 A table named %table% already exists. This upgrade cannot be applied to this database until this situation is resolved.
19041 There is no table named %table% in this database. This upgrade cannot be applied to this database until this situation is resolved.
19042 There are currently %count% records in table %table% that are in state %value%. This script cannot be applied unless no records are in this state. You must first transition these records to another state and then apply this upgrade again.
19043 Unsupported numeric scale: %scale%.
19044 Error encountered when configuring a DSN. Error Code: %errcode% - %mesg%.
19045 Invalid or corrupted connect-options string "%opts%".\nValid format is: key=value;key=value
19047 Invalid value "%value%" for connect-option "%key%".\nValid values are: %valid%
19048 No connect options are defined for this vendor.
19049 The connect options specified for this database will use "long" datatypes, but the database was made with Oracle-8 "clob" datatypes. You must use Oracle 8 client and server software to access this database. Also, ensure that you have *NOT* specified the connect option "LOB_TYPE=LONG".
19050 The connect options specified for this database will use Oracle-8 "clob" datatypes, but the database was made with "long" datatypes. You must either use Oracle 7 client software to access this database or add the option "LOB_TYPE=LONG" to the ClearQuest connect-options field for this database.
